Description

Slowmist problem description:

The use of saturating_add , saturating_mul , and saturating_sub in Rust is generally intended to prevent
integer overflow and underflow, ensuring that the result remains within the valid range for the data type. However, in
certain cases, relying on these functions alone can lead to inaccurate or unexpected results. This occurs when the
application logic assumes that saturation alone guarantees accurate results, but ignores the potential loss of
precision or accuracy..

Our response:

We assumed that we were losing precision though is better to throw an error in such case. Suggested changes have been applied.

Types of changes

What types of changes does your code introduce?

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)